The sponsor side of MuviPe — Tiny cost. Massive reach. A sponsor pays
to put a creative in front of the audience the Theatre already has, and every rupee
of that has to be tracked, split, and reported back with the same rigour as a ticket.
Where the producer sells access to a title, the sponsor pays for attention around
one — a creative placed in front of the audience the Theatre already draws,
priced and tracked with the same discipline as a ticket.
Sponsored, before anything elsepriority orderIn-house sponsor inventory fills first. Third-party ad networks are the fallback for whatever sponsor demand doesn't cover, not the default source.
The player is not the platformthe whole pointThe delivery mechanism that actually plays a creative is a capability, not a product — it knows how to play what it's handed, and nothing about which creative to hand it, who's eligible, how much budget is left, or what any of it costs. Every one of those decisions belongs to MuviPe, not to the player.
Player vs. decisioning
The player is the very last step: play this file, on this screen, now. Everything
before that step — the actual work of running a sponsor product — is a
separate layer that hands the player its answer and nothing more.
What each layer actually owns
Player
Decisioning
Plays whatever file it's handed
Chooses which creative gets handed to it
No concept of a sponsor or a budget
Checks the sponsor still has budget left
No concept of "this viewer, again"
Applies frequency capping per viewer
No concept of cost or payout
Resolves the commission split, tracks spend
Reports back that it played
Turns that report into a billable event
One dumb step at the end of a long pipeline
Everything a sponsor product actually is — targeting, eligibility, budget, frequency capping, cost — happens before the player is ever involved. By the time the player receives anything, every decision has already been made; it just has to render the result.
02
Lifecycle
Sponsor registration
A sponsor account isn't live the moment it's created — it's a state machine,
the same way a producer account is granted rather than self-served. Registration
collects legal/display name, contact, location, business category, website, and a
tax identifier before anything moves forward.
Fig 1. Five states lead to active; three off-ramps can end the relationship at any later point, not just at review.
What each ordinary state means
State
Meaning
REGISTERED
Legal/display name, contact, country/state/city, business category, website, tax identifier submitted.
EMAIL_VERIFIED
Confirms the account holder is real.
PROFILE_COMPLETED
Every registration field finished.
UNDER_REVIEW
Awaiting an admin decision.
APPROVED → ACTIVE
Cleared to run campaigns and spend.
03
Delivery
Creative → player → tracking
A player only ever plays what it's told to. Everything before that —
deciding which creative, for whom, within what budget — and everything after
— knowing whether it actually played — is MuviPe's own layer, not something
any playback capability provides on its own.
Fig 1. Decisioning and tracking are the two layers that don't exist inside any playback capability — they're where MuviPe actually owns the sponsor relationship.
What the player doesn't give you
No campaign conceptoursNo campaign/creative management, no targeting, no frequency capping, no budget pacing, no sponsor billing, no revenue split, no hosted ad server. All of it sits above the player, not inside it.
Tracking is the billing triggermeasurementAn impression or a completed view is what makes an event billable. Everything downstream — commission, reporting, spend against budget — starts from that one signal.
Counted twice, on purpose
Playback beacons are counted client-side, but ad-blockers routinely drop them, which quietly undercounts real impressions. A second, server-side count taken at the moment a slot is decided — not when it's watched — exists purely to reconcile against that gap, so a sponsor's bill isn't at the mercy of whichever viewers happen to run an ad-blocker.
04
Full Flow
Campaign → viewer → billing
Registration, delivery, and the commission and billing machinery described next,
tied together end to end for one actual viewing session. An
in-stream ad and a banner ad are not the same shape — a banner has no duration,
so it has no "skip" and no "fully watched" the way a video does. Two separate flows,
not one flow with a checkbox.
In-stream (pre-roll / mid-roll)
Everything up to and including the player was already covered under Delivery. What
follows fills in the piece that wasn't shown yet: what happens after the creative
starts playing, and the three genuinely different things a viewer can do with it.
Fig 1. Three genuinely different outcomes, not one event with a flag. A viewer can skip and still click through moments later — click isn't downstream of the other two, it's independent of them.
Skipped earlypartial viewThe viewer left before the creative finished. Something still happened — the slot was filled, an impression occurred — but it's a weaker signal than a completed view, and is tracked as its own distinct event type rather than folded into "watched."
Watched fullycompletionThe creative played to the end uninterrupted. The strongest signal a playback ad can give, and the event the earlier VAST design doc calls out as the one that should feed a viewer's own reward path (a scratch card) as well as the sponsor's billing.
Campaign visitintent, not attentionThe viewer actively clicked through to wherever the sponsor's campaign points. This can happen whether the creative was skipped or watched fully — it's a click, not a playback state, and it's tracked as its own event regardless of what the other two recorded.
Three event types, one resolution path
Whichever of the three happens, the event still resolves through the same commission-profile chain described next, and lands in the same sponsor ledger. What differs is only the event type recorded and, eventually, what that type is worth — not the machinery that processes it. What each type is actually worth relative to the others isn't decided in this document; it's an admin-controlled rate, the same way the storage overage rate is.
Banner (static placement)
A banner has no duration to interrupt, so it has no skip and no "fully watched."
It's on screen or it isn't, and the viewer either looked past it or clicked it.
Fig 2. Two outcomes instead of three — no duration means no skip and no completion, only whether the click happened.
No skip, no completionstructural, not a gapMissing on purpose, not an oversight — a static image has no timeline for a viewer to abandon or finish. The only two states that make sense are whether it was seen and whether it was clicked.
Never mid-playbackdifferent surface entirelyA banner lives on browse surfaces — home, an interstitial between screens — not inside a title's own playback session the way a pre-roll or mid-roll does. It competes for a different moment of a viewer's attention.
Same resolution path regardlessshared machineryAn impression or a click here resolves through the identical commission chain and lands in the identical sponsor ledger as an in-stream event. The format differs; the billing and reporting machinery underneath doesn't.
05
Commission
Profile resolution
Not one flat rate across every sponsor, and not a rate hand-set per creative either.
The split is resolved at the moment of charge by walking up a chain until a profile
is actually defined.
Fig 1. Whichever level actually has a value wins — resolution stops at the first one found, walking right until it does.
The platform default is the flooralways resolvesEvery creative eventually resolves to a split, because the bottom of the chain is never empty. It's the same shape as the ticket engine's own payout split — owner / platform / service / distributor / GST — reused rather than reinvented.
Placement outranks nothing by defaultset onceA pre-roll slot is worth more than a footer banner, so placement gets its own default above the platform floor — set once, not negotiated per campaign.
Overrides are the exceptionrare, deliberateA campaign- or creative-level override is NULL almost always. Setting one is reserved for a sponsor with a genuinely bespoke contract — the exception path, not a knob every campaign is expected to turn.
One engine, not two
Resolving a sponsor commission doesn't invent new payout math — it walks this chain to a split, then hands off to the same engine that already pays out the ticket tree. Sponsor money and ticket money are computed differently but paid out through one mechanism.
06
Wallet & Ledger
Two separate books
A sponsor's spend is its own book, kept with the same discipline as the platform's
user-facing ledger — but never the same book. Different money, different parties.
Append-onlyno editsThe wallet, the ledger, and each campaign's allocation of it are all append-only records. History is never rewritten — a correction is a new entry, not a change to an old one.
No mutable running totalby designA campaign's spend is never a single number that gets decremented in place. Adjusting it always means an explicit transaction with a reason attached — an audit trail survives every correction, not just the current balance.
Fig 1. Two ledgers with the same discipline — append-only, reason-coded corrections — but no shared rows. A sponsor's spend and a user's earnings never sit in the same table.
07
Reporting
Two different questions
A sponsor and an admin are asking genuinely different questions about the same
inventory, so they get genuinely different views — never one dashboard with a
role-based filter bolted on.
Sponsor viewtheir own onlyCampaign summary, spend, impressions, audience — aggregated, and scoped strictly to that sponsor's own campaigns. Never a glimpse of another sponsor's numbers, and never individual viewer identities.
Admin viewinventory efficiencyFill rate, unused inventory, revenue per placement — "how efficiently did we monetise the inventory we have," which is a platform question, not a sponsor one. Kept deliberately separate rather than as a superset view.
08
Storage
Free tier & overage
A sponsor's creative library isn't free to host either — every banner, video,
or sponsored-tile asset uploaded gets stored on the same CDN a producer's titles
live on. The rule is the same shape as the producer's, scaled to what a creative
library actually needs.
5GBfree, per sponsor
∞uploads never blocked
₹/GBset by admin, not fixed
The allowance
5GB, freeper sponsorEvery sponsor's creative library — every banner, every video asset, summed across every campaign — carries this much storage at no cost. Far smaller than a producer's 500GB, because a creative library is banners and short clips, not a catalogue of full titles.
Past it, storage is billedoverageOnce a sponsor's library crosses 5GB, the bytes past that line stop being free. Nothing about the upload itself changes — only whether that space now carries a cost.
How it's enforced
Never a blocksame rule as producerCrossing the line doesn't stop a sponsor from uploading a new creative mid-campaign. The platform keeps accepting assets regardless of how far over the free tier a sponsor's library has gone.
A warning, acknowledgedconsent, not a gateThe sponsor sees a warning the moment they're into paid territory: their library has exceeded the free allowance, and further storage carries a charge. They accept that before continuing.
Fig 1. Identical decision shape to the producer's storage rule — only the free-tier number and what's being uploaded differ.
Same rate mechanism as the producer side
The overage rate here isn't a separate number the platform invents for sponsors — it tracks the same underlying CDN cost the producer overage rate does, set by admin and free to move when that cost does, rather than being fixed in the product and going stale.